fix(run): key presentation repair fairness by stable ID - #140

Why

Follow-up to #136. Bounded presentation repair currently stores a positional cursor inside restart/flapping state and consumes the incidental order of each drift plan. That couples presentation to lifecycle accounting and makes progress sensitive to plan ordering.

What

Give presentation repair its own stable-ID cursor and carry it across supervisor passes.

How

• sort pending presentation patches by PTY stable ID;
• resume after the last attempted stable ID across passes;
• keep the cursor separate from flapping state;
• preserve lifecycle-first execution and the existing eight-patch bound;
• exercise reversed input and persistent failures to prove deterministic coverage without starvation.

Rationale

Presentation projection is idempotent metadata reconciliation. Its retry/fairness state should be keyed by the same stable identity it repairs and remain outside lifecycle/flapping accounting.

Verification

• deterministic two-pass presentation repair unit test;
• lifecycle-first bounded-batch integration test with reversed presentation input.